Configuring the export settings

The settings in the Export section of a configuration file are used by the Global Collaboration Framework export processors. This section contains the settings described in the following table:

Export settings
Setting	Description
AssemblySyncOpt2	When set to True, enables the alternative assembly export method. The default is False.
BrcFormat	Format of the briefcase files created by the GCF: RAR, ZIP, or BRC. The default is brc.
DoNotTransferBrc	When set to True, the export processor will not transfer briefcases; they will be left in the folder specified in the OutPath option. A special task must then be scheduled to transfer the briefcases. The default value is False; the export processor will transfer the briefcases normally. Note Normally, the export processor creates briefcases and starts a separate process to transfer them to the target share. The process first checks whether there is already a transfer process running to the same target share. If there is a process already running, the second process terminates. In most cases, this works fine. This option is for special situations where the export processor fails to detect an instance of itself that is already running. The result is that the same briefcase will be processed by multiple instances of the transfer processor. The evidence of this is when there are a lot of errors in the transfer log that read “failed to transfer, permission denied”. To work around this, set this option to True and schedule a special transfer task using the syntax: GCFTransferProc.exe <IniFile> <TargetShare>
ExportRenditions	When set to 1, renditions are included with the documents that are exported. If a briefcase format other than brc is specified in BrcFormat, a valid format definition must exist in the vault's configuration as described in the BlueCielo Meridian Enterprise Configuration Guide. The identical format definition must also exist in the configuration file of theBlueCielo Project Portal share. When set to 0, renditions are not included.
FullLog	When set to 0 or omitted, only errors and high-level events are added to the log file. When set to -1, detailed events are logged that can be useful for troubleshooting.
LogPathOut	The path to the folder containing the log files generated by the export processor.
OutPath	The path to the folder where outgoing briefcases are created.
ParallelTransfer	When set to False, the transfer processor transfers briefcases as in older versions of GCF. The default value is True, so it can be omitted. This is for backward compatibility only. Note This should be set to False when the collaborating sites share the same GCF computer, including use with GCF/Project Portal.
ProjectPortalSyncModifiedDocs	When set to True, the export processor searches for and sends modified documents to Project Portal. The default is False.

Export settings

Setting

Description

AssemblySyncOpt2

When set to True, enables the alternative assembly export method. The default is False.

BrcFormat

Format of the briefcase files created by the GCF: RAR, ZIP, or BRC. The default is brc.

DoNotTransferBrc

When set to True, the export processor will not transfer briefcases; they will be left in the folder specified in the OutPath option. A special task must then be scheduled to transfer the briefcases. The default value is False; the export processor will transfer the briefcases normally.

Note Normally, the export processor creates briefcases and starts a separate process to transfer them to the target share. The process first checks whether there is already a transfer process running to the same target share. If there is a process already running, the second process terminates. In most cases, this works fine.

This option is for special situations where the export processor fails to detect an instance of itself that is already running. The result is that the same briefcase will be processed by multiple instances of the transfer processor. The evidence of this is when there are a lot of errors in the transfer log that read “failed to transfer, permission denied”. To work around this, set this option to True and schedule a special transfer task using the syntax:

GCFTransferProc.exe <IniFile> <TargetShare>

ExportRenditions

When set to 1, renditions are included with the documents that are exported. If a briefcase format other than brc is specified in BrcFormat, a valid format definition must exist in the vault's configuration as described in the BlueCielo Meridian Enterprise Configuration Guide. The identical format definition must also exist in the configuration file of theBlueCielo Project Portal share. When set to 0, renditions are not included.

FullLog

When set to 0 or omitted, only errors and high-level events are added to the log file. When set to -1, detailed events are logged that can be useful for troubleshooting.

LogPathOut

The path to the folder containing the log files generated by the export processor.

OutPath

The path to the folder where outgoing briefcases are created.

ParallelTransfer

When set to False, the transfer processor transfers briefcases as in older versions of GCF. The default value is True, so it can be omitted. This is for backward compatibility only.

Note This should be set to False when the collaborating sites share the same GCF computer, including use with GCF/Project Portal.

ProjectPortalSyncModifiedDocs

When set to True, the export processor searches for and sends modified documents to Project Portal. The default is False.

Note GCF/Project Portal uses the Meridian Enterprise file name without the extension for the corresponding document name in BlueCielo Project Portal. To use a Meridian Enterprise property for the name in BlueCielo Project Portal instead, create a property mapping in the PropertyMappings section of the briefcase option set as described in the BlueCielo Meridian Enterprise Configuration Guide. Following is an example mapping

Related concepts

Configuring the GCF processors

Related tasks

Configuring the general settings

Configuring the import settings